Change tag handling to support generation for Alpha API - #153
Conversation
TKIPisalegacycipher
left a comment
There was a problem hiding this comment.
Line 127 ends with "7 products" -- this can now be "8 products".
Merge remote-tracking branch 'upstream/master'
|
Re: I had accidentally removed the meraki folder and had to restore it. When I did so, git converted the line breaks, so that's why this file is part of this commit. warning: CRLF will be replaced by LF in |
|
Thank you for submitting this. I tested these changes, and it breaks library generation for GA. We will not make these changes for the time being. |
|
To preserve library generation for GA/Beta branches, I moved this logic to an optional flag (-p ). So, to build for Alpha, you can use the following syntax: Using the regular generation command will continue to operate as usual for GA/Beta builds. |
|
Thanks @joshand ! This is a step in the right direction. However, there are other parts (like action batches) which would require additional logic. We will undertake this effort when the MT team is ready to GA their endpoints. In the meantime, it's hard to justify the additional work and testing that would be required to integrate this into the main branch. These commits make more sense in a separate development branch. Would you like to open a devel branch? |
In the current build script, we are currently limiting to first 10 tags, which excluded environmental. I've expanded this to 11 in order to stop the crash. This might result in correct environmental APIs, but I've not actually tested this.